Ticket-Based Harvest Life Cycle Information Management: System and Method

ABSTRACT

A system and method is presented for gathering data concerning harvests. Data tickets are generated at a point of origination (i.e., the field), local storage, processing, or a customer location. Data tickets may also be generated for supplies delivered to the field. Implements attached to a vehicle in the field (e.g., a tractor) may provide data over a vehicle communication bus about how a field processing task was performed. Data may be extracted from the bus to use in preparing a field processing ticket, possibly in combination with manual entry from field personnel. A harvest data tracking system, based on data tickets, may be used to track the complete life cycle of crop production.

RELATED APPLICATIONS

The present application is a continuation of U.S. patent applicationSer. No. 13/832,661, filed on Mar. 15, 2013, which in turn is acontinuation-in-part application of U.S. patent application Ser. No.13/551,916, filed on Jul. 18, 2012, which in turn claimed the benefit ofU.S. Provisional Application 61/508,819, filed Jul. 18, 2011, all ofwhich are hereby incorporated by reference.

FIELD OF THE INVENTION

The present application relates to the field of automated harvestmanagement. More particularly, the described embodiments relate to asystem and method for tracking planting, field processing, andharvesting in mining, agricultural, and forestry industries throughmanual or automated data ticket processing.

SUMMARY

The presented embodiments disclose a flexible, cloud-based tool thatprovides an automated method to record the harvest and distributionprocess, and tools to meet unique requirements of farming operations.The system integrates with a farm's existing infrastructure to captureand record data necessary in order to secure harvested crops from thefield to the point of delivery. The system also integrates with forestryand mining inventory to secure harvested wood or mining products fromthe point of origination to the point of delivery.

The disclosed embodiments provide unprecedented control over harvestsecurity, updating critical data on a daily or even real-time basis.Issues are identified. Compounding problems are prevented. Workers areheld accountable. Accurate accounting is possible. All of whichtranslates into improved transparency for stakeholders: bankers,investors, insurance agents and most importantly, the farmer, forester,or miner.

Through use of the disclosed system and method, farmers, foresters, andminers accurately track and trace key harvest and distributionactivities. This is accomplished by:

-   -   recording weights and quality levels for material harvested at        the field or forest level, or mined at the mine level.    -   recording and tracking product stored in point of origin        storage.    -   recording product transportation activities on a per load basis.    -   recording product loads delivered to internal storage        facilities.    -   recording product weights and quality levels for loads delivered        to customers.    -   extracting information about field processing (e.g., seeding,        fertilizing, cutting, baling) from a bus (e.g., ISOBUS) over        which implements in a vehicle (e.g., tractor) communicate        task-specific information.    -   reconciling all activities and view product data in real time.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram showing locations that can be used tosource, store, process, or receive the goods from a farm, forest, ormine.

FIG. 2 is a schematic diagram showing the components of a system thatgathers, stores, and processes data in accordance with one embodiment ofthe present invention.

FIG. 3 is a schematic diagram showing a three-ticket process that takesgoods from a field, stores the goods in local storage, and then deliversthe goods from storage to a customer.

FIG. 4 is a schematic diagram showing a two-ticket process that takesgoods from a field to a customer.

FIG. 5 is a schematic diagram showing a five-ticket process including aprocessing step.

FIGS. 6A-6F shows screen shots from a ticket creation softwareapplication running on a mobile device, with 6A showing a home screen,6B showing a cart ticket entry screen, 6C showing a field to storageticket entry screen, 6D showing a field to customer ticket screen, 6Eshowing a storage to customer ticket entry screen, and 6F showingadditional data entry fields from the storage to customer ticket entryscreen.

FIG. 7 is a schematic diagram showing system capable of ticketgeneration without human interaction.

FIG. 8 is a schematic diagram showing data movements for input materialsfor farming.

FIG. 9 is a schematic diagram illustrating a communication bus (e.g., anISOBUS), on a vehicle such as a tractor, wherefrom data about implementsused by the vehicle in the field may be extracted.

FIG. 10 is a flowchart illustrating a process for preparation of a dataticket using information from a communication bus (e.g., an ISOBUS), ona vehicle such as a tractor.

FIG. 11 is a schematic diagram illustrating possible components of aharvest data extractor on the communication bus.

FIG. 12 is a schematic diagram illustrating a complete life-cycle—fromseed supplier to consumer of the harvest—that may be tracked, verified,and analyzed using a ticket-based system.

DETAILED DESCRIPTION Overview

The present invention can be used to track goods that are obtainedthrough farming, forestry, mining, drilling, and similar processes. Forinstance, agricultural crops such as corn or cotton are ideal candidatesfor tracking through the disclosed embodiments of the present invention.In addition, lumber obtained through harvesting forests can also betracked, as can coal or other materials that are removed from the earththrough mining, and oil, natural gas, and other hydrocarbonic materialsremoved from the earth through drilling. The current description willdescribe the use of the present invention in connection with farming.Nonetheless, it should be clear that the same systems and processes canbe used in these other contexts as well.

FIG. 1 shows four key locations where the harvest data is to beobtained. In particular, data is to be obtained at the field 110 (orforest or mine) where the product to be tracked originates. In addition,data is to be obtained at local storage facilities 120 where the crop(or other product) can be stored temporarily after being collected. Datais also obtained at processing facilities 130, such a cotton gin or cropdrying facility that processes or transforms the crop in some way.Finally, data is obtained when products or crops are delivered to acustomer 140 that pays the farmer for their crop. These differentlocations 110-140 are shown connected by some type of transport 150. Thetransport 150 may be a truck, train, barge, pipeline, or any othertransportation mechanism.

By tracking data about a crop at various locations, it is possible toaccumulate comprehensive data about a farmer's harvest in a way that hasnot been previously possible. It is important to track this data at thelocations 110-140 specified in FIG. 1 because it is at these locationsthat a crop must be carefully monitored for potential loss or otherevents. For instance, it is important for a farmer to confirm that theamount of crop taken off the field and delivered to a trucking firm isthe same as the amount of crop received and paid for by the farmer'scustomer. In addition, monitoring the crop at these locations alsoallows the farmer to analyze their business for profitability. Forexample, by tracking the crop that comes off each field 110, the farmercan determine the comparative yield for each field. These results can becompared to the inputs (such as seed, fertilizer, pesticides, labor)that created that crop in each field to determine whether changes inprocedures might increase the profitability of a farm.

FIG. 2 shows one system 200 that can be used to track this harvest data.In this system, a plurality of handheld devices 210, 212, 214 are usedby the farmer to obtain data about the harvest. For instance, a workerin the field cart can record on handheld device 210 information abouteach cartload of a crop that is delivered to a semi truck fortransportation. This information can include the field where the cropwas harvested, the time and date of that harvest, an identifier for thefield cart being operated by that worker, the weight of the crop thatwas delivered to the semi, the particular semi that received the crop,and the driver of that semi. Additional information could also becollected, such as descriptors about the weather (sunny, cold, etc.) anddescriptions about the crop (healthy, wet, etc.). Similarly, anotherworker can use handheld device 212 to receive information about thedelivery of the crop from that semi to the farmer's local storagefacility 120, while a third worker can use handheld device 214 to recordinformation about deliveries made directly to customers 140.

Data relating to the receipt of crops at the various data gatheringlocations 110-140 is recorded on the handheld devices 210-214 as data“tickets.” Data tickets contain data, typically in a plurality ofstructured data fields, concerning a transfer of a crop from onelocation to another. The devices 210-214 then transmit these datatickets over a network 220 to a remote server 230, which then stores thedata in a database 240. In one embodiment, the network 220 is a widearea network such as the Internet. The handhelds 210-214 can access theInternet 220 through a WiFi network. Frequently, the handhelds 210-214will be gathering data in locations that do not have WiFi access easilyavailable, such as in a farmer's field. In one embodiment, the handhelds210-214 allow input of data even when the device does not have networkaccess. This data is cached in local storage on the device. Thehandhelds 210-214 then periodically determine whether access to thenetwork 220 is available. If so, data cached in the local storage isthen sent to the server 230 over the network 220.

In another embodiment, the handheld devices 210-214 include cellularcapabilities, such as smart phones or tablet computers using Apple's iOS(from Apple Inc., Cupertino Calif.) or the Android operating system(from Google Inc., Mountain View, Calif.). These types of devices canfrequently transmit data over the Internet 220 using cellular datanetworks. With such capabilities, data can be transmitted to the server230 immediately upon data entry as long as the device 210 is withinrange of a cellular tower with data capabilities. Even with thisembodiment, the devices 210-214 are preferably designed to cache datawhen the network 220 is not immediately available.

The data is accumulated in database 240, and then made available to thefarmer through a back office computer 250 operating over the samenetwork 220 and server 230 that was used to collect the data from theremote handheld devices 210-214. In other embodiments, different ormultiple physical servers could perform the function of the server 230shown in FIG. 2 without altering the scope of the present invention.

The back office computer 250 accesses the database 240 throughprogramming provided by the server 230, ideally through a web browser orother thin client operating on the computer 250. In effect, datacollection and data analysis for the farmer are provided using asoftware-as-a-service model. The farmer pays the operator of the server230 and database 240 for the right to store data in the database 240 andto use software operating on the server 230 to analyze this data. Thisfrees the farmer from the headaches of maintaining the network andserver needed to store and backup the data. Meanwhile, the operator ofthe server 230 and database 240 offers the same service to multiplefarmers.

The data analysis software provided to the back office computer 250allows the farmer to compare payments received from a customer (asevidenced through settlement documents and delivery receipts from thecustomer) with data tickets specifying the amount of crop that wasdelivered to that customer. Furthermore, the farmer can verify that theamount of crop taken from the fields is equivalent to the crop that waseither delivered to a customer or is otherwise in storage. This type ofreconciliation is extremely valuable for farmers, especially since thisdata is almost immediately available given the nature of the data ticketsubmission described herein. Reconciliation errors that indicate missingcrop can be immediately tracked down to a particular worker, piece ofequipment, date, and time. In addition, the analysis software availablethrough the back office computer can also give the farmer the ability toanalyze the productivity of individual fields in a way that was nototherwise possible for most farmers.

The server computer 230 and the back office computer 250 includes a setof software instructions or interfaces stored on a non-volatile,non-transitory, computer readable medium such as a hard drive or flashmemory device. A digital processor, such as a general purpose CPUmanufactured by Intel Corporation (Mountain View, Calif.) or AdvancedMicro Devices, Inc. (Sunnyvale, Calif.) accesses and performs thesoftware. To improve efficiency, processor may load software stored inits non-volatile memory into faster, but volatile RAM. The database 240can be stored on the same non-volatile memory used by the servercomputer 230 for its operating system, or on a different memoryaccessible by its process such as an external direct access storagedevice (or DASD). The database 240 consists of both data and softwareinstructions informing the server computer 230 how to access, analyze,and report on the data in the database 240.

The computers 230, 250 further include a network interface tocommunicate with other computerized devices across a digital datanetwork such as network 220. In one embodiment, the network is theInternet, and the network interfaces on the computers 230, 250 includeTCP/IP protocol stacks for communicating over the network 220. Thenetwork interface may connect to the network wirelessly or through aphysical wired connection. Instead of being a single computer with asingle processor, the server 230 could also implemented using a networkof computers all operating according to the instructions of thesoftware.

Ticket Generation

FIG. 3 shows a typical process 300 used by a farmer to track cropscoming off a field 110. In this process, a combine 112 in the field 110takes the crop off the field 110. Periodically, the combine 112transfers its load to a field cart 114, which then takes its load to oneor more waiting semi trucks 152 for transport 150. In this embodiment, adata ticket 310 is created when the crop is transferred from the cart114 to the semi 152. This first data ticket 310 is referred to as acart-to-truck ticket (or simply “cart ticket”) 310. In this embodiment,the cart ticket 310 is created by a worker operating the field cart 114.Using their handheld device 210, the worker opens an application (orapp) that operates on the device 210. The worker logs into the app, sothat the app knows the worker's identifier, the particular field beingworked by the worker, as well as an identifier for the cart 114 beingoperated by the worker. When the transfer is made to the semi 152, theworker tells the app to create a cart ticket 310. The worker must inputor verify the crop, identify the semi 152 and the driver of the semi,and then input the amount of crop transferred to the semi 152. In mostembodiments, the cart 114 has an integrated scale. The app requests thatthe worker input the weight on the scale before and after the transferto the semi, with the calculated difference being the amount of the croptransferred to the semi. The worker may also include descriptors aboutthe current weather conditions or the condition of the crop (i.e.,“wet”) with the data transmitted in the cart ticket 310.

In FIG. 3, the cart ticket 310 is the first ticket created, and is alsocalled ticket 1. In some embodiments, the driver of the semi also has ahandheld device 212, and the semi truck also contains a scale. In theseembodiments, the semi driver will also create a cart ticket 310 (i.e.,ticket 1 b) indicated the amount of crop received from the cart 114, andthe identifier of the cart and the cart operator. While these two carttickets 310 contain essentially the same information, the creation oftwo tickets allows comparisons between the tickets and the ability todetect and correct faulty data from one of the tickets. Because the datais mostly duplicative, however, some embodiments would create only asingle cart ticket 310.

In the process 300 shown in FIG. 3, the semi driver delivers their loadto a local storage facility 120 on the farm. This storage facility mayinclude a plurality of storage bins, including storage bin 122. When theload from the semi truck 152 is transferred to the storage bin 122, asecond ticket (known as a field-to-storage ticket) 320 is created. Thisticket 320 can be created by the operator of the truck 152 using the apprunning on their handheld device 112. Like the cart ticket 310, thefield-to-storage ticket 320 contains information about the deliveryequipment (semi 152 and the driver) as well as the receiving equipment(storage bin 122). A bin operator may have their own handheld device114, and therefore may create their own version of the field-to-storageticket 320 (ticket 2 b in FIG. 3). Note that since the storagecapabilities of the field carts 114 and the semi trucks 152 are notidentical, there is not a one-to-one correspondence between the carttickets 310 and the field-to-storage tickets 320.

A different semi truck 154 may then be used at a later date to take thecrop from the storage bin 122 and deliver the crop to the customer 140.To track this transaction, the truck driver will create astorage-to-customer ticket 330 to track details about the delivery,including date, time, identifiers for the semi 154 and the driver, theoriginating location (storage bin 122), the receiving location (grainelevator 142 at the customer location 140), and the condition of thecrop (“dry”). The crop condition may be based merely on generalobservations (“dry”), or may be made upon scientific tests establishingvarious characteristics of the crop (i.e., moisture content). Thesetests may be conducted at the farmer's storage facilities 120, at thecustomer's facilities 140, or at both locations.

If the customer participates in the system 200 with the farmer, thecustomer 140 could create a corresponding ticket 330. In most cases,however, the customer 140 does not participate, and instead presents thedriver with a written delivery receipt 340. When payment is made to thefarmer, the payment will likely include a settlement document 350 thatincludes the delivery information found on the delivery receipts 340.Payment associated with the settlement document 350 will relate to aspecific contract 360 between the customer 140 and the farmer.Consequently, to complete the data record in the database 240 for propertracking and reconciliation, it is contemplated that the interfaceprovided by the server 230 to the back office computer 250 includes theability for the farmer to enter information about written deliveryreceipts 340, settlement documents 350, and contracts 360.

FIG. 4 shows a simplified process 400, where the farmer delivers theircrop directly to a customer 140 without storing the grain at a localstorage facility 120. In this case, the transfer from the field cart 114to the semi truck 152 creates one or two first tickets (the cart ticket)410. This cart ticket 410 is effectively the same as the cart ticket 310created in process 300. Rather than transporting the crop to storage120, the semi 152 in process 400 delivers the crop directly the customerelevator 142. When this delivery is made, the truck driver creates asecond ticket known as a field-to-customer ticket 420.

The process 500 shown in FIG. 5 is similar to the processes 300, 400shown in FIGS. 3 and 4, respectively, although process 500 contains moresteps. In this case, the field cart 114 delivers the crop to semi 152,and in the process the operator or operators of these machines create acart ticket 510. The semi 152 delivers the crop to the local storage bin122, and a field-to-storage ticket is created 520 that is much liketicket 320 described above. In process 500, the farmer must pay a thirdparty to process the crop. For instance, if the farmer were growingcotton, the farmer would pay a cotton gin facility to gin the cotton. Asemi 154 is used to transfer to crop to the processor 130. When the cropis delivered to the processor, a storage-to-processor ticket 530 iscreated with details about the semi 154, the semi driver, the amount ofcrop delivered, the condition of the crop, the originating storage bin122, and the specific processing facility of the processor 130 thatreceived the crop.

After the processing is complete, a new semi 156 accepts the processedcrop and delivers the crop back to local storage 120 on the farm. Inthis case, the crop is stored in storage bin 124. A processor-to storageticket 540 is created detailing this transaction. Finally, the processedcrop is taken from storage bin 124 by semi 158 and delivered to customerelevator 142, and a storage-to-customer ticket 550 is created.

In this embodiment, a data ticket is created every time the crop isreceived at the field 110, local storage 120, processor 130, or thecustomer 140. The field related ticket (cart ticket 310, 410, or 510) iscreated when harvesting of the crop (effectively receiving the crop atthe field). By ensuring that a data ticket is created when the crop isreceived at each of these locations, the harvest is effectively trackedand monitored through each movement, storage, processing, and customerdelivery step. It would be possible to create additional data ticketsand still be within the scope of the present invention. However,additional tickets are not necessary to ensure the minimal level oftracking as exemplified in processes 300, 400, and 500.

FIG. 6a shows a mobile device 600 that could be used by an operator of afield cart 112 or semi truck 152, or an individual working at a storagelocation 120, processing location 130, or customer site 140. The mobiledevice 600 includes a processor (such as those created under the ARMarchitecture developed by ARM Holdings, Cambridge, UK) and tangible,non-transitory memory that contains both computing instructions(software) and data. The computing instructions include an applicationor “app” that allows the user to create data for the database 240. Asexplained above, this data is created in the form of tickets thatcontain data about a particular event relating to the receipt of productat one of the key locations 110-140. In the preferred embodiment, thisapp runs on a general purpose operating system, such as Apple's iOS orGoogle's Android operating system. Furthermore, the preferred mobiledevice 600 includes network capabilities to allow the device 600 tocommunicate with the server 230 over the network 220. This could beprovided by a WiFi or cellular network interface (or both) locatedwithin the device. Finally, the preferred device 600 includes locationdetection capabilities that can identify the location of the device 600.This helps in numerous situations, including the automatedidentification of a farmer's field in a cart ticket 310, 410, or 510.The device 600 is preferably a smart phone, a tablet computer, or anyother similar device.

The app operating on the mobile device 600 creates a home screen 610,which provides the user with the ability to change information about theuser by selecting change button 620. Information about the user,including the equipment or location being managed by the user can beentered into the app at this stage so that it doesn't need to beseparately entered for each ticket created by the app.

The home screen 610 also includes a cart ticket button 630, afield-to-storage ticket button 640, a field-to-customer ticket button650, and a storage-to-customer ticket button 660. Each of these ticketcreation buttons 630-660 bring up an entry screen for the user to enterthe necessary data to create the desired ticket. The entry screen 632for the cart ticket is shown in FIG. 6b , and can be reached by pressingthe cart ticket button 630 on the home screen 610. Similarly, thefield-to-storage ticket entry screen 642 (FIG. 6c ), thefield-to-customer ticket screen 652 (FIG. 6d ), and thestorage-to-customer entry screen 662 (FIG. 6e ) can be reached byselecting buttons 640, 650 and 660, respectively. The ticket entryscreens 632, 642, 652, and 662 allow the user to enter the datanecessary to complete the data ticket. To the extent possible,permissible data has been predefined in the database 240, preferablythrough the back office computer 250. This permissible data isdownloaded by the app running on the mobile device 600, allowing many ofthe fields in the ticket entry screens 632-662 to be filled in throughpull down selection menus. In most cases, the entry screens 632-662contain more data than can be viewed at once on the mobile device.Consequently, the entry screens 632-662 preferably scroll up and down toallow the user to access all of the data fields. FIG. 6f , for example,shows the additional data entry fields that form the storage-to-customerticket entry screen 662 that were not shown in FIG. 6 e.

Automatic Ticket Generation

FIG. 7 shows an alternative embodiment system 700 that allows theautomatic generation of data tickets. This system 700 takes advantage ofthe fact that the tickets created in the previously described embodimentare generated when product is received at a location. In the case ticketgeneration scenarios described above, a piece of equipment that containsthe product is brought into proximity with another piece of equipmentthat will receive the product. The equipment might be the field cart114, the semi 152, the storage bin 122, the grain elevator 142, orequipment at a processing location 130. System 700 takes advantage ofthis fact by detecting the proximity of another piece of equipment, andusing that detection to generate a ticket and to determine the datanecessary to complete the ticket.

This is accomplished by using beacons in field equipment to broadcastequipment location so that when two pieces of equipment are withinsufficient range, the beacon in either piece of equipment can broadcasta signal unique to the piece of equipment that can be recognized by amobile device (e.g. an Android phone or tablet) in the other piece ofequipment. In terms of uniqueness, all that is necessary is that thebeacon be unique in the context in which the equipment is used. In thecontext of a farm utilizing 25 different pieces of farm equipment, thebeacons must be unique to that farm. A beacon would be considered uniqueeven if the beacon utilizes the same signal as a different but remotebeacon not used on the farm. In FIG. 7, a field cart 720 loaded withcrop from the field approaches a semi truck 740, which is waiting forthe cart 720 on a road proximate to the field. The field cart 720contains a scale 722 that weighs the current load on the cart.Preferably, this scale 722 can be wirelessly queried by other devices,which causes the scale to return the current weight of the load carriedby the cart 720.

The field cart 720 also contains a mobile device 730 operating anapplication designed to automatically generate data tickets. A beacon744 on the semi truck 740 continuously or periodically transmits asignal that can be received by a receiver or receiver/transmitter 732 onthe mobile device 730. The app running on the mobile device 730recognizes the beacon as belonging to a particular semi 740.Alternatively the receiver 732 can be located separately from the mobiledevice elsewhere on the field cart 720. For instance, a beacon device724 that transmits a beacon for the field card 720 may also include areceiver that detects the presence of the beacon 744 from semi 740. Thiswould allow the manufacturer of the beacon technology to sell acombination beacon transmitter and beacon detector. When this beacondetector detects the beacon 744, the detector will signal the mobiledevice 730 with information about the beacon 744.

In yet another embodiment, the semi 740 does not have a beacon device744 to signal its presence. Instead, a mobile device 750 on the semi 740has its own transmitter and receiver device 752. The transceiver couldbe, for instance, a WiFi transceiver sending and receiving signalsaccording to one of the IEEE 802.11 standards. A similar transceiver 732in the mobile device 730 riding in the field cart 720 would detect thepresence of the signal from the mobile device 750. The presence of thissignal could inform the mobile device 730 in the field cart of thepresence of the semi's mobile device 750. At this point, field cartmobile device 730 could consult an internal or external database tolearn information about whether the semi mobile device 750 is currentlyoperating. Alternatively, the field cart mobile device 730 couldestablish a network or other data connection with the semi mobile device750 after that device 750 is detected. The two mobile devices 730, 750could then exchange data stored in each device 730, 750 about how eachdevice, 730, 750 is currently being used.

For example, the mobile device 730 could monitor its WiFi receiver todetect the presence of another mobile device transmitting a WiFi signal.The strength of the signal received can be used to determine the nearestmachine. Once the signal from the semi's mobile device 750 is received,the two devices 730, 750 establish a communication interface or link. Inthis way, the field cart mobile device 730 learns that the field cart720 has approached a particular semi 740 currently being driven by aparticular operator.

When the semi's beacon 744 is detected, or the signal from the semi'smobile device 750 is received and understood, the field cart mobiledevice 730 then begins to query and monitor the scale 722 operating onthe field cart 720. Alternatively, the mobile device 730 may be capableof extracting and reading other equipment related data streams, such asspeed, acceleration, braking, and dumping from the field cart 720. Theapp on the mobile device 730 can interpret the mechanical activity datagenerated from the equipment in which the smart device is located (i.e.,that the cart is unloading its load) or can monitor changes in the scale722 to see that the load in the cart has lessened. By intelligentlymonitoring these on-cart devices, the mobile device 730 will be able totell when a transfer of the product has completed, and also will be ableto tell the amount of product that has been transferred. By combiningthis information with the beacon data (which other equipment 740 is nearor nearest the cart 720), the mobile device can detect the need togenerate a ticket, complete the data in the ticket, and transmit theticket to the server 230, all without any user intervention.

In FIG. 7, the field cart 720 and the semi truck 740 each have beacons724, 744 and each have smart devices 730, 750, respectively. The semi740 may be parked next to the field currently being harvested, such ason an access road. The semi 740 remains on the road waiting to befilled, and might be located next to other semi trucks (not shown inFIG. 7). When the field cart 720 is full, the operator drives to theside of the field and approaches the trucks. The field cart 720 stopsclosest to the first semi truck 740 in line to unload.

The smart device 730 in the cart 720 may receive a data stream fromdevices on the cart 720 indicating that the cart 720 is stopped. Themobile device 730 will sense the beacon data from beacon 744 anddetermine which semi truck 740 is closest to the device 730. The device730 will next sense that the cart 720 is unloading from the data streamfrom the monitoring equipment on the cart 720 (such as scale 722). As aresult the smart device will have the capability to generate an activityrecord (a cart ticket) that documents the following:

-   -   Activity date    -   Activity time    -   Activity type    -   Initiating equipment (grain cart id—signed into the device)    -   Initiating operator (grain cart driver—signed into the device)    -   Receiving equipment (truck id—recognized from the truck beacon    -   Receiving operator (recognized from the truck beacon)    -   Activity location (from the smart device and or device GPS)    -   Truck weight (from scale data collected by smart device)

Similarly, a smart device 750 in the truck 740 will be able to createdata tickets as well. If the system 700 was so set up, the truck'sdevice 750 could create a corresponding cart ticket based on readingsfrom its own scale 742, and information obtained from the beacon 724operating on the cart 720. If the truck had no internal scale 742, it ispossible that the device could obtain this information directly from thescale 722 on the cart 720, or the weight data could be simple left blankand extracted from the cart ticket created by the cart 720 when thetickets are received and analyzed by the server 230.

When the truck 740 then delivers its load to the farmer's storagefacility or to a customer, a new ticket could be created (afield-to-customer or a field-to-storage ticket), also with out operatorintervention. A beacon could be set up at either location, therebyallowing the process to repeat much as when the cart 720 approached thesemi truck 740. Alternatively, there may be no beacon at the destination(which may be likely when delivering the load to a customer). To allowthe automatic creation of a ticket in these locations, the device 750 onthe truck would know that the load was now to be delivered to somelocation after it detected the loading of the semi 740 from the fieldcart 720. Since the device 750 cannot rely upon beacon information todetermine its delivery location, the device 750 instead relies on GPSlocation. This GPS location can be determined from a GPS or otherlocating technology that is internal to the device 750 (such technologyis commonly found in phones and tablet computers running the Androidoperating system or Apple's iOS) or by reading a GPS device on the truck740 itself. This generated ticket could include the followinginformation:

-   -   Activity date (from smart device)    -   Activity time (from smart device)    -   Activity type (internal storage location or customer delivery,        as determined from the GPS on a smart device or from a beacon at        the delivery location)    -   Supplying equipment (from the Grain Cart Beacon)    -   Supplying operator (from the Grain Cart Beacon and system)    -   Activity locations (field and dump location) from GPS in smart        device    -   Weight data (from the GC ticket matched by the system or read by        the device at the scale house via Bluetooth)

This type of scenario applies to all of the activity ticket-based datacreation and collection in harvest processes as well as in inputmanagement processes. The ability to sense and record related equipmentand equipment proximity in a new and unique way enables smart devices infield equipment to auto generate activity tickets without userintervention. Importantly, this type of scenario applies broadly to ahost of harvest or input management activities across a multitude ofsimilar industries including: forestry (harvesting and planting oflumber and trees), mining (harvesting minerals), energy (harvesting oiland natural gas), or any agricultural sector.

Inputs

The system described above is used to track crops or similar goods thatare harvested from a location. As described in the above-identifiedpriority provisional application, one embodiment of the currentinvention can also be used to track inputs at farmer fields. These“inputs” may constitute seeds for planting the crop in the field. Otherinputs include fertilizers, pesticides, or herbicides that are sprayedor spread on a field to improve crop yields. As shown in FIG. 8, datatickets are created when input materials are moved between differentlocations 810, 820, 822, and 830. More particular, input related datatickets are created when inputs are received in inventory 820 or 822after purchase from a source or store 810, are taken from inventory 820,822 to be used in the field 830, are returned unused from the field 830and placed back into inventory 820, 822, are moved from one inventorylocation 820 to another 822, and are returned from inventory 820, 822 tothe store 810. Transport and other farm vehicles and equipment 840provide the ability to move the inputs between these locations 810, 820,822, and 830. In some embodiments, the transporting equipment 840 hasweights, scales, and other measuring devices to help determine thequantity of inputs that are moved or applied by the vehicles 840.

As was the case in managing and tracking harvests, the tickets that arecreated to manage and track inputs have a different name and containdifferent data depending upon the movement being tracked. A “contractdelivery ticket” is used to record the input (i.e., the product) andquantity that is received from the store 810 and put into inventory 820,822 after purchase. This ticket would record the date of delivery andthe inventory location 820, 822 that received the input. A contractdelivery ticket can be created using a remote handheld (such as device210 shown in FIG. 2) by the worker that received the input intoinventory, or by back office personnel using the back office computer(such as computer 250 of FIG. 2).

A “load out ticket” is created when an input is taken out of inventory820, 822. This ticket creates the input product, the quantity ofproduct, the originating inventory location 820, 822 of the input, theequipment that received in the input, and the equipment operator. The“field application ticket” is used to recording planting, spraying, orspreading an input on a field 830. The field 830 on which an input isused, and the time at which the input was applied, is recorded in thefield application ticket. In some embodiments, the field applicationticket is submitted to the remote server 230 when the field applicationis completed, which allows the worker that completes the ticket toindicate whether the application to that entire field 830 has beencompleted. This allows the system 200 to track the completion of inputapplication tasks on a field-by-field basis. A “field return ticket” isused to indicate that some of the inputs that were taken out ofinventory 820, 822 through a load out ticket were not used on the field830 (as indicated in the field application ticket) and are thereforereturned into inventory 820, 822.

If inputs can be stored in multiple storage or inventory locations 820,822, transfer tickets track the movement of inputs between theselocations. A “transfer out ticket” indicates that the input has beenremoved from one location 820, and a “transfer in ticket” indicates thatthe input as been received at a second location 822. “Supplier returntickets” are used to indicate that input in inventory 820. 822 has beenreturned to the originating supplier 810 for a refund.

These input related tickets can be generated in the same manner as theharvest tickets. In other words, the tickets can be created manually inthe field by workers using remote handheld devices 210-214, or can becreated automatically using beacons and scales that are detectable andaccessible to the devices 210-214 as described above. The tickets can bedesigned to refer to only one type of input at a time. If multiple typesof inputs are removed from inventory 820, 822 for application on field830, multiple input tickets would be used to track this movement.Alternatively, and preferably, tickets can be designed to allow thetracking of different inputs on a single ticket.

By tracking both inputs and harvests, a farmer can compare yield resultsto input applications on a field-by-field basis. In addition, the farmercan manage and track inventory of inputs and harvests, which helps thefarmer prevent loss, identify spoilage and shrinkage points, and developa greater understanding of their business.

CAN Bus

In order to improve the data that is received along with the tickets inthe above-described embodiments, it is possible to integrate the ticketgeneration process with data collected over the CAN bus of the equipmentdelivering the inputs or managing the harvest on a field. FIG. 9 shows aISOBUS integrated system 900 that can be used in this environment. Thesystem 900 is designed around an ISOBUS 901, which is a vehicle bus fortransmitting messages between components on vehicles including farmequipment. The ISOBUS 901 is a CAN bus system operating in compliancewith ISO standard 11783, which is a communication protocol for CAN bussystems that are used in forestry and agricultural tractors andimplements. The ISO 11783 standard provides a standard for control andcommunications over a CAN bus that allows for tractors and implementsfrom different manufacturers to inter-communicate.

The bus 910 provides communication and control signals between a tractor911 (or other vehicle) and various implements 939 associated with orattached to the tractor 911. A tractor 911 may use various devices 920that are “inputs” to the process of growing crops, such as a planter921, to sow seed, or a sprayer 922, for pest/weed control. The tractor911 may also use output devices 930, such as a combine 931 forharvesting crops and a baler 932 to compress and compact raked crops.Each such implement 939 may have an individual controller. Thecontrollers may be connected to the bus 901, placing the implementsunder a common control system, with manual controls entered through auser interface of a virtual terminal 910. Through a user interface, thevehicle operator might toggle among the various implements by a simpleselection through a control. Time-dependent information about the stateand operation of the connected implements 939, as well as about thetractor 911, is transmitted across the bus 901. Depending uponimplementation, GPS 950 location of the vehicle 911 might be acquiredfrom the bus 901, or might be acquired through a connection to awireless phone network or WiFi network.

Information available over a bus 901 may be accessed for tracking inputsand outputs to the farming (or forestry or mining) process and, inparticular, for preparing, verifying, and/or supplementing data tickets971. A data ticket 971 might be prepared for any number of tasks in thefield; for example, treatment of a field (e.g., with fertilizer orpesticide); processing of a field (e.g., raking); planting seed;harvesting a crop; or transferring any crop or substance between fieldvehicles. A harvest data extractor 970 may be connected to the bus 901for this purpose. The harvest data extractor 970 communicates, possiblyover a communications system 960, with a device such as a tabletcomputer 990, a mobile phone, or a device that is convertible between atablet and a computer such as the Microsoft SURFACE®. There are a numberof means whereby the communication could be accomplished. The dataextractor 970 might communicate wirelessly, via BLUETOOTH® or otherpersonal area network, if the tablet 990 is close enough. Detection of“close” might be done by an exchange of signals, a handshake, betweenthe devices. The data extractor 970 might communicate with the tabletcomputer 990 over WiFi or cellular phone network, if available.Depending upon configuration, the tablet 970 might be connected to thedata extractor 970 with a wire, for example, by a USB connection.Alternatively, the information might be transferred without a network orwired connection in two steps: (1) a transfer to tangible media (e.g.,flash drive, DVD) from the data extractor 970; and (2) a transfer fromthe media to the tablet computer 990, possibly through some interveninginterface. Note that the communication system(s)/means used forcommunication between the harvest data extractor 970 and the tabletcomputer 990, or other device in that role, might be different from thecommunication system(s)/means used for communication between the harvestdata extractor 970 and a third party server 980.

FIG. 10 illustrates a process for preparing a data ticket 971 frominformation acquired from the bus 901, possibly combined withinformation provided by personnel in the field. After the start 1000,the vehicle performs 1010 some task using an implement 939 that ismonitored by the bus 901. Task-specific information is transferred 1020from the implement 939 to the bus 971. The data extractor 970 extracts1030 information pertaining to the task from the bus 971. The dataextractor 970 may process 1040 the data in any number of ways, ormaintain the data in raw form. Processing may include, for example,subsampling (e.g., saving a variable less frequently than the intervalthat is available on the bus); summarizing (e.g., computing averages orother statistics); combining two or more types of data to produce somecomposite data (e.g., combining moisture content and wet weight toestimate dry weight); or otherwise analyzing the data (e.g., to drawconclusions, such as whether the extracted data is consistent with datafrom other sources, such as operator entry). When the task with theimplement 939 is completed, a person may manually enter 1050 thatinformation into a data ticket 971. In the embodiments illustrated byFIG. 10, the relevant information from the data extractor 970 istransferred 1060 to the tablet computer 990, and that information isincorporated 1070 with, or added to, manually entered information aboutthe task into the data ticket 971. The data ticket is uploaded 1080 to aserver 230 (possibly after some exchanges at intermediate points wheresupplies or product or transferred and data tickets are created, such ashave already been described). From the server, information from the bus901 may be accessed, possibly remotely by a farmer or by the manager ofthe data ticket system, and used 1090 to verify manually-enteredcontents of the data ticket 971 and/or for comparison with otherinformation acquired from data tickets from various stages in plantingor harvesting, or with other data. The process ends 1099. Note that insome embodiments, some of the steps might be performed in a differentorder, some might be omitted, and/or others added, all within the scopeof the inventive concepts.

In other embodiments (not shown), information from the data extractor970 might be uploaded to a server separately from ticket creation,either synchronously or asynchronously. For example, the data extractionmight be performed by a third party, and uploaded to its server, whichis accessible over a wide-area network by users for verification oranalysis.

In general, the concepts and techniques illustrated by FIGS. 1-8 applyto field-task (/field processing/field-to-cart) data ticket 971creation. An implementation of the system might use, for example, any orall of the following: a handheld device 990 to input data for afield-task ticket 971; a user interface on the device to enter dataabout the event that is not created automatically, or redundantly, forcross-checking against automatically generated data; buttons or othercontrols on the handheld device 990 to indicate the type of field-taskticket is being created; access by the handheld device 990 to theInternet using WiFi or cellular communication when available; caching ofinformation on the handheld device 990 when appropriate; beacons totrigger ticket generation or data transfer between devices; WiFidetection by a mobile device to trigger ticket generation or datatransfer; manual ticket 971 generation; and automatic ticket 971generation.

The concepts and techniques illustrated by FIGS. 1-8 also extend toserver 230 storage of a database 240 that includes information gatheredfrom the field-task tickets 971. The database 240 may includeinformation from any or all of the stages in farming illustrated by FIG.12, and be accessed by a back-office computer 250.

FIG. 11 illustrates exemplary components of a harvest data extractor970. A particular harvest data extractor 970 might include some or allof the components shown in FIG. 11, and possibly others. Thesecomponents incorporate logic that is represented in hardware (e.g.,hardware interfaces, processor(s), tangible digital storage), and/or insoftware instructions stored in such storage and accessible forexecution by processing hardware. The components may include:

-   -   Processor 1100;    -   Tangible digital storage 1101 including software instructions        and data, including task-specific data acquired from the bus        901;    -   Interface with vehicle bus 1150;    -   Interface with external communication system(s) 1151, for        transferring data to the tablet computer; uploading data to a        server; and or downloading information from external sources to        use in processing information from the bus 901;    -   Interface with vehicle (or instrument) operator 1152, because        the data extractor 970 itself might be incorporated as a device        on the bus 901 that an operator might access with the virtual        terminal 910;    -   Module 1110 to select types of data to extract from the bus 901;    -   Module 1111 to set timing for how often to select the data        types;    -   Module 1112 to access (send data to/receive data from) the bus        901 and the storage 1101;    -   Module 1120 to transmit (and receive) across external        communications systems;    -   Module 1121 to prepare data tickets (if automatically generated)        or to augment manually prepared data tickets;    -   Module 1123 to respond to triggers that cause events, such as        uploading of data to a server;    -   Module 1130 to request from, or send to, the vehicle operator        pertaining to harvest information tracking.

According to published standards, some examples of types of data thatmight be obtained from an ISOBUS 901 from a data extractor 970 regardinga treatment (e.g., planting, fertilizing, harvesting) include thefollowing:

-   -   Start and end date and time for a task;    -   Operator;    -   Field;    -   Total acres to which treatment is applied;    -   Vehicle speed during application;    -   Gallons of treatment material per acre;    -   Pressure applied when planting seed;    -   Application rate;    -   Fertilizer applied;    -   Insecticide applied.

In addition to the types of information already described regarding datatickets generally, information provided by a vehicle operator or fieldmanager as part of a data ticket 971 relating to a treatment mightinclude, for example:

-   -   Whether treatment of the field was completed;    -   Method of applying the treatment;    -   Temperature;    -   Wind speed;    -   Sky conditions; and    -   Comments.

Recall that in FIGS. 3 and 4, data tickets were created at points oftransfer between vehicles, with weight of the crop loaded onto a vehiclepossibly being an important tracked parameter. Using the communicationbus 901, much more information may be available about the preparation,planting, treatment, harvesting, and clean-up processes, as well as thetangible inputs (e.g., seed, fertilizer, pesticide, insecticide) andoutputs (e.g., crop yield, crop moisture, crop quality) to thoseprocesses. This information can be integrated with the data trackingmanagement process in several ways. In the case of harvesting, afield-processing (or field-treatment) ticket 971 (in this case afield-to-cart ticket) might be prepared that summarizes the crop beingdelivered to the cart. This ticket may include information aboutquantity, but may also include information how the crop was harvestedand its condition. The quantity information might be measured directlyby the implement 939, or in some cases might be calculated from theprocess. For example, from the speed of the vehicle 911, the time spentin a field, the cutting width of a harvester implement 939, andknowledge about crop density, a quantity can be estimated. Although suchan estimate may be less accurate than the weight of a crop in a cart ortruck, it is certainly good enough for a verification of reasonableconsistency about crop quantity with subsequent elements of the deliverychain. The vehicle receiving the crop may prepare a double-entry mateticket 971 b to allow comparison.

Note that some or all data within a field-processing data ticket 971 maybe handled automatically. Data might be extracted, filtered, summarized,or analyzed by the data extractor 970, and transmitted by somecommunication system 960 to a remote location, such as a third partyserver 980, or to a mobile device, such as a tablet computer 990. Thetablet computer 990 might augment the data from the data extractor 970with information such as the name of the operator of the vehicle, or thefield being harvested or prepared. The tablet 990 might then transmitthe data ticket to a remote server. Similarly, a data ticket might beautomatically generated for “input” to the crop production process, suchas how a quantity of seed was applied to a field.

FIG. 12 illustrates a beginning-to-end sequence tracking production 1200of food or other crop (or, analogously, mining or forestry product) thatmight be captured using embodiments of the invention. The process startswith “sources”, suppliers 1205 that provide inputs 1210, such as seed1211, fertilizer 1212, and pesticides 1213. There are phases of inputtransport 1220, such as have already been described in this document. Inthe field 1240, data extraction from the buses 901 of vehicles providesinformation about what was planted 1241, how the field and crop 1250were prepared and processed 1242, and what was harvested 1243. The crop1250 goes through phases of output transport 1260 to consumers 1270(“sinks”) of the product, such as customers 1271 or storage 1272.Addition of field 1240 phase single or double-entry account to theaccounting, at each point of transfer of input items or output items, asillustrated by FIGS. 1-8 and associated description, makes the lifecycle accounting complete.

The many features and advantages of the invention are apparent from theabove description. Numerous modifications and variations will readilyoccur to those skilled in the art. For example, the above descriptionexplained that various software programs can be running on mobiledevices that operating in various crop-related machines or at variouscrop-related locations. Many aspects of the present invention would beequally novel if these mobile devices were fixedly mounted in theselocations so that they were no longer technically mobile. Furthermore,many aspects of the present invention remain novel even if thetechnology running these applications were embedded directly into themachinery or locations involved. Since such modifications are possible,the invention is not to be limited to the exact construction andoperation illustrated and described. Rather, the present inventionshould be limited only by the following claims.

1. (canceled)
 2. A method, comprising: a) extracting a value from awired communications bus on a farm vehicle performing a task, the valuebeing indicative of a quantity of a material carried by the farm vehicleto perform the task; b) receiving user input on a physical userinterface of a computing device, the user input relating to the task; c)at the computing device, preparing a data ticket containing datarelating to the task, the data ticket containing first data derived fromthe value extracted from the wired-communications bus and second dataderived from the user input received on the physical user interface; andd) transmitting the data ticket onto a digital communication network. 3.The method of claim 2, further comprising performing the task using thefarm vehicle, the task selected from the set consisting of planting,fertilizing, harvesting, cutting, baling, applying herbicide, andapplying pesticide.
 4. The method of claim 2 wherein the value isindicative of a change of the quantity of material.
 5. The method ofclaim 2, wherein the value is indicative of a rate of application ofmaterial.
 6. The method of claim 2, wherein the value is indicative ofthe weight of crop carried by the farm vehicle.
 7. The method of claim2, wherein step a) extracts a plurality of values over a time period. 8.The method of claim 7, further comprising analyzing the plurality ofvalues to generate the first data, wherein the analyzing is selectedfrom a set of analysis tasks consisting of subsampling, summarizing, andcombining multiple types of data.
 9. The method of claim 7, wherein thewired communication bus is an ISOBUS or other CAN bus.
 10. The method ofclaim 2, wherein the user input specifies a process used in performingthe task.
 11. The method of claim 2, wherein the computing device isselected from a set consisting of a portable computer, a tabletcomputer, and a cell phone.
 12. The method of claim 2, furthercomprising the step of identifying discrepancies between the value andthe user input.
 13. A method, comprising: a) performing, using animplement attached to a farm vehicle, a task selected from the setconsisting of planting, fertilizing, harvesting, cutting, baling,applying herbicide, and applying pesticide; b) transmitting an implementvalue from an implement over a wired communications bus on a farmvehicle, the implement value indicative of an amount of material relatedto the performed task; c) receiving, by a data extraction device, theimplement value from the wired communication bus; d) generating afield-task ticket describing the results of the task using the implementvalue received by the data extraction device; b) interpreting a receivedwireless signal as a triggering event; and e) upon detection of thetriggering event, transferring the field-task ticket onto a digitalcommunication network.
 14. The method of claim 13, wherein thetriggering event indicates proximity to another vehicle or to astructure.
 15. A method, comprising: a) at a computing device, receivinga value that was extracted from a wired communications bus on a farmvehicle performing a task, the value being indicative of a quantity of amaterial carried by the farm vehicle; b) at the computing device,receiving user input on a physical user interface of the computingdevice, the user input relating to the task performed by the farmvehicle; c) at the computing device, preparing a data ticket containingdata relating to the task, the data ticket containing first data derivedfrom the value extracted from the wired-communications bus and seconddata derived from the user input received on the physical userinterface; and d) transmitting the data ticket onto a digitalcommunication network.